Utility meter emulation mode system and method

ABSTRACT

One embodiment describes a utility metering system that includes metering infrastructure that facilitates data communication within the utility metering system in accordance with an expected metering platform, and a utility meter communicatively coupled to the metering infrastructure. The utility meter operates in a native mode when a native metering platform is compatible with the expected metering platform, in which the utility meter operates in a first manner in accordance with the native metering platform. The utility meter operates in an emulation mode when the native metering platform is not compatible with the expected metering platform and an emulation metering platform is compatible with the expected metering platform, in which the utility meter operates in a second manner in accordance with the emulation metering.

BACKGROUND

The subject matter disclosed herein relates to metering systems and morespecifically, to metering platforms utilized in utility meters.

Generally, a utility meter may monitor consumption of a utility service,such as electrical power, natural gas, or water. More specifically, autility meter may interface with meter programs, advanced meteringinfrastructure (AMI), billing systems, and the like. For example, theutility meter may transmit billing data, such as energy usage data, to autility provider's billing system to bill the consumer according tovarious communication protocols, such as American National StandardsInstitute (ANSI) C12.18. Additionally, the billing data may becommunicated in data tables, such as those defined by American NationalStandards Institute (ANSI) C12.19. However, as new metering platformsare developed, the new metering platforms may be incompatible with themeter programs, AMIs, and/or billing systems designed to interface withprevious metering platforms. For example, because new metering platformsmay aim to improve on previous platforms, the data collected, thecommunication protocols, and/or the user interfaces may differ fromprevious platforms. Similarly, meter programs, AMIs, and/or billingsystems designed to interface with metering platforms designed byvarying manufactures may also be incompatible.

Accordingly, it would be beneficial to enable a utility meter tointerface with meter programs, AMIs, billing systems, and the likedesigned for other metering platforms. For example, this may includeenabling the utility meter to emulate the functionality and/or interfaceof a different metering platform.

BRIEF DESCRIPTION OF THE INVENTION

Certain embodiments commensurate in scope with the originally claimedinvention are summarized below. These embodiments are not intended tolimit the scope of the claimed invention, but rather these embodimentsare intended only to provide a brief summary of possible forms of theinvention. Indeed, the invention may encompass a variety of forms thatmay be similar to or different from the embodiments set forth below.

A first embodiment describes a utility metering system that includesmetering infrastructure that facilitates data communication within theutility metering system in accordance with an expected meteringplatform, and a utility meter communicatively coupled to the meteringinfrastructure. The utility meter operates in a native mode when anative metering platform is compatible with the expected meteringplatform, in which the utility meter operates in a first manner inaccordance with the native metering platform. The utility meter operatesin an emulation mode when the native metering platform is not compatiblewith the expected metering platform and an emulation metering platformis compatible with the expected metering platform, in which the utilitymeter operates in a second manner in accordance with the emulationmetering.

A second embodiment describes a utility meter that includes memory thatstores a native metering platform related to operation of the utilitymeter in a first manner, and one or more emulation metering platformsrelated to operation of the utility meter in a second manner. Theutility meter also includes a processor that selectively switchesbetween implementing the native metering platform and implementing oneor more of the one or more emulation metering platforms stored in thememory. The utility meter emulates functionality, interface, or both ofa non-native metering platform when the processor implements anemulation metering platform that corresponds to the non-native meteringplatform.

A third embodiment describes a non-transitory tangible computer-readablemedium storing a plurality of instructions executable by a processor ofa utility meter to determine an expected metering platform of meteringinfrastructure coupled to the utility meter, in which the meteringinfrastructure facilitates data communication with the utility meter inaccordance with the expected metering platform, determine whether anative metering platform implemented in the utility meter is compatiblewith the expected metering platform, enter an emulation mode when thenative metering platform is not compatible with the expected meteringplatform, in which the native metering platform relates to operation ofthe utility meter in a first manner, and implement one or more emulationmetering platforms to emulate functionality, interface, or both of theexpected metering platform when the utility meter is in emulation mode,in which the one or more emulation metering platforms relates tooperation of the utility meter in a second manner.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a schematic diagram illustrating a utility distribution andmetering system including utility meters, in accordance with anembodiment;

FIG. 2 is a block diagram illustrating components of a utility meter ofFIG. 1, in accordance with an embodiment;

FIG. 3A is an example of a native data table of the utility meter ofFIG. 2, in accordance with an embodiment;

FIG. 3B is an example of an emulated data table of the utility meter ofFIG. 2, in accordance with an embodiment;

FIG. 4 is a flow chart describing entering an emulation mode, inaccordance with an embodiment;

FIG. 5A is a native user interface of the utility meter of FIG. 2, inaccordance with an embodiment; and

FIG. 5B is an emulated user interface of the utility meter of FIG. 2, inaccordance with an embodiment.

DETAILED DESCRIPTION OF THE INVENTION

One or more specific embodiments of the present invention will bedescribed below. In an effort to provide a concise description of theseembodiments, all features of an actual implementation may not bedescribed in the specification. It should be appreciated that in thedevelopment of any such actual implementation, as in any engineering ordesign project, numerous implementation-specific decisions must be madeto achieve the developers' specific goals, such as compliance withsystem-related and business-related constraints, which may vary from oneimplementation to another. Moreover, it should be appreciated that sucha development effort might be complex and time consuming, but wouldnevertheless be a routine undertaking of design, fabrication, andmanufacture for those of ordinary skill having the benefit of thisdisclosure.

When introducing elements of various embodiments of the presentinvention, the articles “a,” “an,” “the,” and “said” are intended tomean that there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

As discussed above, a utility meter may monitor utility consumption byinterfacing with meter programs, advanced metering infrastructure (AMI),service provider billing systems, and the like. As used herein, meterprograms, advanced metering infrastructure (AMI), service providerbilling systems, and the like may generally be referred to as “meteringinfrastructure.” However, because some metering infrastructure isdesigned to interface with a specific metering platform, such meteringinfrastructure may be incompatible with newer metering platforms and/ormetering platforms designed by other manufactures. Theseincompatibilities may result from differing data collected/stored, thecommunication protocols utilized, and/or the user interfaces. Theseincompatibilities may delay consumer and/or utility provider adoption ofnewer or different metering platforms.

Accordingly, one embodiment of the present disclosure describes autility metering system that includes metering infrastructure thatinterfaces with an expected metering platform, in which the meteringinfrastructure is compatible with the expected metering platform, and autility meter communicatively coupled to the metering infrastructure.The utility meter includes a native mode, in which the utility meter isin the native mode and implements a native metering platform when thenative metering platform is compatible with the expected meteringplatform. The native metering platform is a metering platform native tothe utility meter. The utility meter further includes an emulation mode,in which the utility meter is in the emulation mode and implements anemulation metering platform when the emulation metering platform iscompatible with the expected metering platform. The emulation meteringplatform is a metering platform non-native to the utility meter. Inother words, utility meters may interface with various meteringinfrastructures by utilizing an emulation mode. As used herein,“emulation mode” is intended to describe a mode that allows a utilitymeter to emulate (e.g., perform in a manner similar to) other meteringplatforms (e.g., a non-native metering platform). In some embodiments,the emulation mode may enable the utility meter to emulate thefunctionality and/or interface of another metering platform. Forexample, the utility meter may communicate emulated data tables that aresubstantially the same as data tables generated by the metering platformbeing emulated (e.g., emulated metering platform).

By way of introduction, FIG. 1 describes a utility distribution andmetering system 10. More specifically, the utility distribution andmetering system 10 distributes a utility services to various consumers12 from a utility provider 14 and monitors (e.g., measures) theconsumption by the consumers 12 via utility meters 16. As depicted, theutility provider 14 distributes utilities to the various consumers 12through a distribution network 18. For example, when the utilityprovider 14 is providing electrical power, the distribution network 18may be an electrical grid. Accordingly, the utility provider 14 mayinclude power generation stations (e.g., using gas, coal, biomass, andother carbonaceous products for fuel), alternative power generationstations (e.g., using solar power, wind power, hydroelectric power,geothermal power, and other alternative sources of power), waterprocessing plants, gas processing plants, and the like. To simplify thefollowing discussion, the utility provided will be described aselectrical power; however, in other embodiments, other utilities such aswater or natural gas may also be distributed.

Additionally, as described above, the utility meters 16 monitor theconsumption of the various consumers 12, which may include commercialand/or residential consumers. As depicted, each consumer's usage may bemonitored by a separate utility meter 16. In some embodiments, theutility meters 16 may be single-phase or poly-phase electric meters.Additionally or alternatively, the utility meters 16 may be a smartmeter such as an I-210 ANSI Meter or a kV2c ANSI Meter, made availableby General Electric Company of Schenectady, N.Y. Each utility meter 16may gather data that characterizes the consumer's consumption such asenergy usage, maximum energy demand, minimums energy demand, demandinterval length, time of use (TOU) calendars, status information, andthe like. The gathered data may then be communicated to the utilityprovider 14 via a first communication network 20.

For example, a utility meter 16 may communicate the gathered data (e.g.,utility usage data) to the utility provider's billing system 22. In someembodiments, the energy usage data may include total active energy usage(e.g., kWh) and maximum energy demand (e.g., kW) to enable the utilityprovider 14 to bill the consumer 12. Accordingly, the billing system 22may be included in one or more computing devices, such as a workstation,mobile device, or desktop computer. Additionally, the firstcommunication network 20 may be wired, wireless, or both. For example, autility meter 16 may wirelessly communicate with a handheld meter readeror communicate via a smart grid. In some embodiments, the firstcommunication network 20 may include advanced metering infrastructure(AMI) to enable two-way communication between the utility provider 14and the utility meters 16. For example, this may enable the utilityprovider 14 to schedule disconnection or connection of utility services,automatic meter reading (AMR), load shedding/control, smart gridapplications, outage reporting, and the like.

Furthermore, the gathered data may also be communicated back to theconsumer 12 via a second communication network 24, which enables theconsumer 12 analyze his/her utility usage. In some embodiments, the datamay include utility usage data, load profile data, time of use (TOU)data, or any combination thereof. More specifically, some consumers 12may utilize a meter program 26 to view meter diagnostics, display timeof use (TOU) schedules/calendars, view alerts, record usage, and thelike. Accordingly, in some embodiments, the meter program 24 may beincluded in a computing device, such as desktop computer, laptopcomputer, or mobile device.

To facilitate the above described features, the utility meters 16 mayinclude various components, such as a communication interface 28, one ormore processor 30, memory 32, a display 34, a user input interface 36,and meter inputs/filtering components 38, as depicted in FIG. 2. Morespecifically, the various data, such as utility usage data, may becollected by the utility meter 16 via the meter inputs and filtercomponents 38 from various sensors, such as current or voltage sensors.Accordingly, in some embodiments, the meter inputs and filter components38 may include voltage and current inputs, one or more ADCs, andfrequency filtering components.

As depicted, the meter inputs and filter components 38 are operativelycoupled to the processor 30 to communicate the collected data to theprocessor 30. More specifically, the processor 30 may perform variousmonitoring and/or control functions. For example, the processor 30 maytime align meter measurements received from the meter inputs andfiltering components 38. To facilitate these various functions, theprocessor 30 is also be communicatively coupled to memory 32, which mayinclude volatile and/or non-volatile memory that stores content, data,instructions or the like. For example, the memory 32 may be a tangiblenon-transitory medium that may store data transmitted to/from theutility meter 16 as well as software applications, instructions, or thelike that enable the processor 30 to perform steps associated withoperation of the utility meter 16. More specifically, as will bedescribed in more detail below, the memory 32 may store, and theprocessor 30 may run, either or both of a native mode and an emulationmode. As used herein, “native mode” is intended to describe a mode thatallows a utility meter to utilize its own (e.g., native) meteringplatform, while “emulation mode” is intended to describe a mode thatallows a utility meter to emulate other metering platforms (e.g., anon-native metering platform).

Additionally, the display 34 and the user input interface 36 enable auser (e.g., the consumer 12 or the service provider 14) to interactdirectly with the utility meter 16. For example, the display 34 maycommunicate information to the user by displaying information such asenergy usage, instantaneous power usage, error messages, meter status,and the like. Accordingly, the display 34 may be a light-emitting diode(LED) display, a liquid crystal display (LCD), or the like. The userinput interface 36 may receive user inputs. For example, the user inputinterface 36 may enable the user to configure the meter 16, selectdifferent information to display, and the like. Accordingly, the userinput interface 36 may includes a keypad, a joystick, a touch-screendisplay, a data input device (e.g., CD-Drive or USB port), or the like.

Furthermore, the utility meter 16 may interface with the firstcommunication network 20, the second communication network 24, or bothvia the communication interface 28. In other words, the communicationinterface 28 enables the utility meter 16 to communicate with theutility provider 14 (e.g., billing system 22) and/or the consumer 12(e.g., meter systems 26). In some embodiments, the data communicated toand from the utility meter 16 may be communicated in data tables, forexample as defined by ANSI C12.19 or IEC 61968. Additionally, thecommunication interface 28 may enable the utility meter 16 tocommunicate in accordance with various communication protocols, suchAmerican National Standards Institute (ANSI) C12.18, ANSI C12.21, ANSIC12.22, International Electrotechnical Commission (IEC) 61107, IEC62056, or any combination thereof.

However, as described above, various metering platforms may differ inthe data collected/stored, communication protocols, and/or userinterfaces. More specifically, the metering platforms may collectdifferent measurements. For example, a first metering platform maysimply collect the total active energy usage (e.g., kWh), whereas asecond metering platform, in addition to collecting total active energyusage, may collect total reactive energy usage (e.g., kVArh) and totalapparent energy usage (kVAh). The storage of the collected data may alsodiffer. For example, the first metering platform may store collecteddata in engineering units (e.g., kWh), whereas the second meteringplatform may store collected data as raw values. Additionally, themetering platforms may utilize differing communication protocols. Forexample, the first metering platform may utilize the ANSI C12.18communication protocol, whereas the second metering platform may utilizeIEC 62056. Furthermore, the metering platforms may interact with a userdifferently. For example, the first metering platform may simply displayenergy usage (e.g., kWh), whereas the second metering platform maydisplay a cumulative demand (e.g., kW) in addition to energy usage.

As described above, the differences between various metering platformsmay cause some metering platforms to be incompatible with meteringinfrastructure (e.g., billing systems 22) designed for other meteringplatforms. Additionally, users (e.g., consumers 12 and/or utilityprovider 14) may be unfamiliar with differences in the user interface(e.g., display 34 and/or user input interface 36). As can beappreciated, this may delay the approval and adoption of new meteringplatforms. Accordingly, as described above, a utility meter 16 mayemploy an emulation mode. As will be described in more detail below, theemulation mode does not merely enable backwards compatibility. Instead,the emulation mode enables the utility meter 16 to mimic (e.g., emulate)the functionality and/or interface of a different metering platform. Insome embodiments, to metering infrastructure, a utility meter 16 inemulation mode appears identical to the metering platform being emulated(e.g., emulated metering platform. In other words, the utility meter 16may collect the same data, store the data in the same format,communicate using the same communication protocol, interact with a userin the same manner, or any combination thereof even when it includes anative metering platform different than the one being emulated.

To help illustrate the functionality of the emulation mode, FIG. 3Adepicts a native data table 40 and FIG. 3B depicts an emulation datatable 42. As used herein, “native data table” is intended to describe adata table generated when the utility meter 16 is in native mode, and“emulation data table” is intended to describe a data table generatedwhen the utility meter 16 is in emulation mode. More specifically, FIGS.3A and 3B depict embodiments of Current Register Data Tables (e.g.,Table 23), in accordance with ANSI C12.19. As depicted, both the nativedata table 40 and the emulation data table 42 include the number ofdemand resets (i.e., NBR_DEMAND_RESETS 44). For example, in the depictedembodiments, the NBR_DEMAND_RESETS 44 is 251. In some embodiments, thismay indicate the number of demands requested because the demand is resetafter each request.

Additionally, the data tables 40 and 42 include the data to becommunicated in data blocks (e.g., TOT_DATA_BLOCK 46 and TOT_DATA_BLOCK48). As depicted, the emulation TOT_DATA_BLOCK 48 includes more datafield as compared to the native TOT_DATA_BLOCK 46. More specifically,the native TOT_DATA_BLOCK 46 includes a first summation (i.e.,SUMMATIONS [0] 50) and a first demand (e.g., DEMANDS [0] 52) while theemulation TOT_DATA_BLOCK 48 additionally includes a second summation(e.g., SUMMATIONS [1] 52), a third summation (e.g., SUMMATIONS [2] 54),and a second demand (e.g., DEMANDS [1] 56). It should be noted that thedata tables 40 and 42 are merely illustrative of the techniquesdescribed herein. In other words, even though the native data table 40may include fewer data fields, operating in native mode may provide morefunctionality than operating in emulation mode with an emulationmetering platform (e.g., prior generation).

The differences between the data blocks 40 and 42 may result fromdifferences between the native metering platform and the emulatedmetering platform. For example, as in the depicted embodiment, theemulated metering platform may be designed to collect and/or communicatemore pieces of data. Illustratively, the native metering platform maycollect and/or communicate the total active energy usage (e.g.,SUMMATIONS [0] 50), the maximum demand (e.g., DEMAND 58), and a timeassociated with the maximum demand (e.g., EVENT_TIME 60). On the otherhand, the emulated metering platform may collect and/or communicate thetotal active energy usage (e.g., SUMMATIONS [0] 50), the total reactiveenergy usage (e.g., SUMMATIONS [1] 62), the total apparent energy usage(e.g., SUMMATIONS [2] 64), the maximum demand (DEMAND 58), a timeassociated with the maximum demand (e.g., EVENT_TIME 60), the minimumdemand (e.g., DEMAND 66), and a time associated with the minimum demand(e.g., EVENT_TIME 68). It should be noted that data collected by theutility meter 16 is merely illustrative. For example, some utilitymeters may not collect the minimum demand.

As described above, to compensate for the differences between variousmetering platforms, the utility meter 16 may enter an emulation mode.For example, when in emulation mode, the utility meter 16 may generatethe emulated data table 42 to interface with metering infrastructuredesigned to interface with the emulated metering platform. In someembodiments, the emulated data table 42 is identical to a data tablegenerated by the emulated metering platform. As depicted, similar fields(e.g., SUMMATIONS [0] 50 and DEMANDS [0] 52) may be populated with datarepresentative of the same information. However, the data may berepresented differently because standards governing the data tables(e.g., ANSI C12.19) often provides for flexibility in quantity types,formats, or number of quantities to name a few. However, utility meters16 sometimes may only implement a specific subset of the standardssupported by the utility meter 16. For example, in the depictedembodiment, the total active energy usage (e.g., SUMMATIONS [0] 50) isrepresented in floating point engineering units (e.g., 1.02201984 e4) inthe native data table 40 and in fixed point raw values (e.g., 1419472)in the emulated data table 42. More specifically, the raw values may beconverted to engineering units by multiplying a register multiplier anddividing a register divisor. For example, in the depicted embodiment,the raw value (e.g., 1419472) is multiplied with the register multiplier(e.g., 72) and divided by the register divisor (e.g., 10,000) to resultin 10220.1984 kWh. Accordingly, to populate the emulated data table 42,the utility meter memory 32 may store the collected data in both thenative format (e.g., engineering units) and emulated format (e.g., rawvalues or primary units), or one format (e.g., native or emulated) andvarious multiplies/divisors to enable conversion to a different format.The DEMANDS [0] 52 may be populated similarly.

On the other hand, different fields (e.g., SUMMATIONS [1] 62, SUMMATIONS[2] 64, and DEMANDS [1] 56) may be populated based on the datacollected/stored in the utility meter memory 32. For example, in thedepicted embodiment, because the utility meter 16 may not collect/storethe total reactive energy usage and the total apparent energy usage,SUMMATIONS [1] 62 and SUMMATIONS [2] 64 are populated with zeroes.Additionally, even though not included in the native data table 40, theutility meter may collect/store a minimum demand and event time value inthe utility meter memory 32, and populate DEMANDS [1] accordingly. Insome embodiments, the utility meter 16 may always collect the minimumdemand and event time, whereas in other embodiments, the utility meter16 may only collect the minimum demand and event time while in emulationmode. In other words, the utility meter 16 may collect data (e.g.,minimum demand and event time) even though it will not be includedwithin the native data table 40. Thus, although the emulated data table42 may be generally compatible with metering infrastructure designed forthe emulated metering platform, additional design considerationsregarding the data collected/stored in the utility meter may be made,such as the types of data (e.g., various fields of data) and the formatof the data (e.g., engineering units or raw values). In someembodiments, the type of data collect and the storage format of the datamay be based on the metering infrastructure receiving the emulation datatable 42. For example, based on the described example, a billing system22 may require the minimum demand (e.g., DEMANDS [1] 56) but not requirethe total reactive energy usage (e.g., SUMMATIONS [1] 62 and SUMMATIONS[2] 64). Accordingly, the processor 30 may instruct the meter inputs 38and the sensors associated with the inputs to collect/store data basedon the utility meter mode (e.g., native or emulation mode) and therequirements of emulated metering platforms.

Based on above description, the utility meter 16 may interface withmetering infrastructure designed for the emulated metering platform byentering the emulation mode and generating emulation data tables 42.Comparatively, a backwards compatible metering platform may merelygenerate data tables compatible with an older metering platform.However, this may constrain what can be done with the utility meter 16and/or make the interfacing with metering infrastructure suboptimal. Forexample, if a previous metering platform is unable to decrypt encodeddata tables, the backwards compatible data tables should be unencrypted.Similarly, an emulation data table 42 generated in emulation mode mayalso be unencrypted. However, the ability to exit the emulation mode andenter the native mode enables the utility meter 16 to generate encryptednative data tables 40, which may improve the security of data (e.g.,data included in native data table 40) output by the utility meter 16.Moreover, the emulation mode enables utility meter 16 to generate one,multiple, or all of the data tables in accordance with the emulatedmetering platform. In some embodiments, this may include data tablesthat define the interface and capabilities of the utility meter 16.

Additionally, for a metering platform to be backwards compatible, themetering platform may be specifically designed to be backwardscompatible with specific previous metering platforms. In other words,the backwards compatibility of the metering platform may be limited byits design. For example, backwards compatibility may constrain operationto extensions of the previous generations (e.g., limiting significantchanges). Comparatively, the present techniques enable emulationmetering platforms to be designed for use in the utility meter'semulation mode. As used herein, “emulation metering platform” isintended to describe a metering platform designed to enable a utilitymeter 16 to emulate another metering platform (e.g., emulated meteringplatform). In other words, the emulation mode increases flexibility incompatibility because the utility meter 16 may emulate various meteringplatforms simply by utilizing a corresponding emulation meteringplatform. In some embodiments, emulation metering platforms mayadditionally be installed in the utility meter 16 after manufacture. Forexample, the utility meter 16 may download emulation metering platformsfrom the utility provider 14 and/or consumer 12 as needed via thecommunication networks 20 or 24. In some embodiments, the emulationmetering platforms may emulate a previous version metering platformand/or a metering platform designed by a different manufacturer. Inother words, the techniques described herein enable the utility meter 16to selectively switch between one or more emulation metering platforms(e.g., emulation mode) and a native metering platform (e.g., nativemode).

One embodiment of a process 70 for selectively switching between thenative metering platform and one or more emulation metering platforms isdescribed in FIG. 4. Generally, the process 70 may include starting inthe native mode (process block 72), determining a metering platformexpected by metering infrastructure (process block 74), determiningwhether the native metering platform is compatible with the expectedmetering platform (decision block 76), and if compatible, remaining inthe native mode (process block 78). On the other hand, if incompatible,the utility meter enters emulation mode (process block 80) and emulatesthe expected metering platform (process block 82).

More specifically, the utility meter 16 may start in its native mode(process block 72) to enable the utility meter 16 (e.g., processor 30,memory 32, communication interface 28, display 34, user input interface36, and/or meter inputs 38) to operate as designed. For example, theprocessor 30 may collect meter measurements via the meter inputs 38 andthe memory 32 may store the measurements as designed. In someembodiments, the utility meter 16 may operate more efficiently whenutilizing its native metering platform because the native meteringplatform is optimized for the particular utility meter 16. Additionally,because the various emulation metering platforms may be designed for usewith the utility meter 16, operating in the native metering platformprovides a baseline for switching to the various emulation meteringplatforms. In other embodiments, the utility meter 16 may remain in itsmost recent metering platform even if the most recent is an emulationmetering platform to reduce the number of metering platform switches.

The utility meter 16 may then determine what metering platform themetering infrastructure is expecting (process block 74). In other words,what metering platform the metering infrastructure is compatible with.In some embodiments, this may include polling the meteringinfrastructure (e.g., billing system 22 or meter program 26). Forexample, the processor 30 may send a request to the billing system 22via the communication networks 20 and 24 requesting an expected meteringplatform, and the billing system 22 may return a response (e.g.,indication) specifying the expected metering platform. The expectedmetering platform may then be determined by the processor 30 andcommunicated to the memory 32 for storage. Additionally oralternatively, the metering infrastructure may push an indication of theexpected metering platform to the utility meter. In other embodiments, auser (e.g., service provider 14 or consumer 12) may directly identifythe expected metering platform to use in the utility meter 16, forexample via the user input interface 36. Furthermore, in otherembodiments, a manufacturer may set the expected metering platform whenthe utility meter 16 is manufactured.

Once the expected metering platform is determined, the utility meter 16determines whether the native metering platform is compatible with theexpected metering platform (decision block 76). For example, theprocessor 30 may compare the native metering platform and the expectedmetering platform stored in memory. In some embodiments, the processor30 may determine that the native metering platform is compatible withthe expected metering platform when they are the same. Additionally oralternatively, the processor 30 may determine that the meteringplatforms are compatible when the native metering platform iscross-compatible with the expected metering platform. In other words, inaddition to utilizing the emulation mode, the native metering platformitself may also be designed to be cross-compatible with other meteringplatforms (e.g., backwards compatible). If the native metering platformis compatible with the expected metering platform, the utility meter 16(e.g., processor 30, memory 32, communication interface 28, display 34,user input interface 36, and/or meter inputs 38) remains in the nativemode (process block 78) and operates in accordance with the nativemetering platform.

On the other hand, if the native metering platform is not compatiblewith the expected metering platform, the utility meter 16 entersemulation mode to enable the utility meter to switch to an emulationmetering platform (process block 80). In some embodiments, the processor30 may retrieve the emulation metering platform from the memory 32. Inother embodiments, the processor 30 may download the emulation meteringplatform via the communication interface 28, for example from theutility provider 14, or user input interface 36, for example from flashdrive, and store the emulation metering platform in the memory 32.

The utility meter may then emulate the expected metering platform byimplementing the emulation metering platform (process block 82). In someembodiments, the processor 30 may instruct the rest of the utility meter(e.g., memory 32, communication interface 28, display 34, user inputinterface 36, and/or meter inputs 38) to operate in accordance with theemulation metering platform. As described above, utilizing the emulationmetering platform may enable the utility meter 16 to be functionallyidentical to the expected metering platform. For example, the processor30 and/or the communication interface 28 may generate an emulated datatable 42 to communicate data with metering infrastructure compatiblewith the metering platform being emulated. Accordingly, users (e.g.,service providers 14 and consumers 12) may implement the utility meter16 with their existing metering infrastructure, which may improve theadoption of the utility meter 16.

Utilizing a process similar to process 70 described in FIG. 4, theutility meter 16 may additionally utilize the emulation meteringplatform to emulate the interface (e.g., display 34) of the expectedmetering platform. Illustratively, a native display 84 is depicted inFIG. 5A and an emulated display 86 is depicted in FIG. 5B. As usedherein, “native display” is intended to describe a display displayedwhen the utility meter 16 is in native mode, and “emulated display” isintended to describe a display displayed when the utility meter 16 is inemulation mode. As depicted, the displays 84 and 86 include similarelements in differing configurations.

More specifically, both displays 84 and 86 include alphanumericcharacters 88, alphanumeric characters 90, energy cycle indicators 92,display units 94, energy delivered indicators 96, and energy receivedindicators 98. In some embodiments, the alphanumeric characters 88 maydisplay energy usage values, instantaneous power usage, and the like;the alphanumeric characters 90 may display a display label or a statuscode (e.g., caution or error); the energy cycle indicators 92 mayindicate the percentage completion of an energy cycle; the display units94 may indicate the measurement units for the alphanumeric characters90; the energy deliver indicators 96 may indicate that energy is beingdelivered to the load; and the energy received indicator 98 may indicatethat energy is being received from the load.

Additionally, the native display 84 includes other elements not includedon the emulated display 86. For example, the native display 84 includestime of use (TOU) indicators 100 that may indicate what time of use rateis in effect; a test mode indicator 102 that may indicate when theutility meter 16 is in a test mode; an alternate display indicator 104that may indicate when the display 34 is in an alternate display mode;voltage phase indicators 106 that may indicate what voltage phase (e.g.,A, B, C) is present; a leading indicator 108 that may indicate totalreactive energy usage (e.g., kVArh) is leading; a lagging indicator 110that may indicate total reactive energy usage (e.g., kVArh) is lagging;an end of interval (EOI) indicator 112 that may indicate an EOIcondition; a continuous indicator 114 that may indicate when the display34 is displaying continuous demand measurements; a cumulative indicator116 that may indicate when the display 34 is displaying continuousdemand measurements; and a previous interval indicator 118 that mayindicate when the display 34 is displaying data from a previous seasonor billing cycle.

As can be appreciated, these additional elements may be unfamiliar tousers (e.g., consumer 12 or utility provider 14). Accordingly, toimprove adoption, the utility meter 16 may utilize an emulated display86 generally identical to a metering platform familiar to the user.Additionally or alternatively, the emulated display 86 may be asimplified version of the native display 84. For example, the simplifieddisplay may display only elements (e.g., alphanumeric characters 88,alphanumeric characters 90, energy cycle indicators 92, display units94, energy delivered indicators 96, and energy received indicators 98)that are generally desired by the user, which, as described above, mayinclude energy usage values, instantaneous power usage, a display labelor a status code, percentage completion of an energy cycle, measurementunits for the display, and whether energy is being delivered to orreceived from the load.

In other embodiments, other aspects of the utility meter 16, such as thecommunication protocol and user input interface 36, may also emulateother metering platforms. For example, the user input interface 36 mayemulate the input configuration utilized in another metering platform.In some embodiments, this may include configuring buttons in the userinput interface 36 to perform similarly to corresponding buttons used inthe emulated metering platform. Additionally, in some embodiments, ifthe user input interface 36 is a touch screen display, the user inputinterface 36 may display a user input interface 36 corresponding withbuttons, labels, configurations, and the like utilized in the emulatedmetering platform. Furthermore, if the native metering platform utilizesANSI C12.18 and an emulated metering platform utilizes IEC 62056-2, theutility meter 16 may enter emulation mode and instruct the communicationinterface 28 to communicate according to IEC 62056-2.

In some embodiments, different aspects of the utility meter (e.g.,display 34 or user input interface 36) may operate in accordance withdifferent metering platforms. For example, the utility meter 16 mayutilize an emulated display 84 while communicating data in native datatables 40. Additionally, the utility meter 16 may utilize an emulatedcommunication protocol (e.g., IEC 62056-2) to communicate with thebilling system 22 while utilizing the native communication protocol(e.g., ANSI C12.18) to communicate with the meter program 26.Accordingly, the flexibility of the utility meter 16 may be furtherincreased because different aspects of the meter may be configuredaccording to various metering platforms. In other words, each aspect ofthe utility meter 16 may be separately configured to operate inaccordance with the native metering platform or an emulation meteringplatform.

Technical effects of the present disclosure include improving thecompatibility of a utility meter 16 with various metering platforms.More specifically, the utility meter 16 may enter an emulation mode toemulate the functionality and/or interface of a different meteringplatform. In some embodiments, this may include utilizing an emulateddata table 42, an emulated display 86, an emulated communicationprotocol, an emulated user input interface, and the like. Accordingly,this may improve compatibility with existing metering infrastructure anduser familiarity. Additionally, the present disclosure enables theutility meter 16 to selectively enter/exit emulation mode, which mayplace less constraints on the design of the utility meter 16.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal language of the claims.

The invention claimed is:
 1. A utility metering system for coupling to ametered component at a metered location for collecting utility data fromthe metered component related to a provided utility service and forcoupling to a metering infrastructure monitoring, collecting andtransferring utility information within the utility metering system froma plurality of coupled utility metering systems in accordance with anexpected metering functionality platform, the utility metering systemcomprising: a utility meter having a processor, a memory, computerexecutable instructions, a first communication interface forcommunicatively coupling over a communication network to the meteringinfrastructure, a second communication interface for communicativelycoupling to the metered component, and a user interface for displayinguser data and receiving user instructions, wherein the computerexecutable instructions are configured to configure the utility meterto: receive over the second communication interface the meteredcomponent of the utility data from the coupled metered component; storethe received metered component of the utility data in the memory; storea native metering functionality platform for communicating over thefirst communication interface with the metering infrastructure; identifythe expected metering functionality platform; compare the identifiedexpected metering functionality platform with the stored native meteringfunctionality platform; operate the first communication interface andthe communicatively coupling with the metering infrastructure in anative mode when the native metering functionality platform is comparedto be the same as or compatible with the expected metering functionalityplatform, wherein the utility meter is configured to operate in a firstoperational manner in accordance with the native metering functionalityplatform, the first operational manner having first operationalfunctions including a first protocol of the first communicationinterface, a first meter operating program, a first type of the utilitydata received and stored, a first operation of the user interface of theutility meter including the first type of the utility data displayed onthe user interface; and operate in an emulation mode when the nativemetering functionality platform is not the same or is not compatiblewith the expected metering functionality platform, wherein the utilitymeter is configured to operate in a second operational manner inaccordance with an emulation metering functionality platform inconjunction with the emulation mode that is compatible with the expectedmetering functionality platform, the second operational manner includeshaving second operational functions including a second protocol of thefirst communication interface, a second first meter operating program, asecond type of the utility data received and stored, a second operationof the user interface of the utility meter including the second type ofthe utility data displayed on the user interface, wherein two or more ofthe second operational functions of the second operational manner aredifferent than the first operational functions of the first operationalmanner of the native metering functionality platform.
 2. The utilitymetering system of claim 1, wherein the utility meter is configured toemulate functionality and the first communication interface, or both ofthe expected metering functionality platform when the utility meteroperates in the emulation mode.
 3. The utility metering system of claim1, wherein the expected metering functionality platform of the meteringinfrastructure comprises a billing system, an advanced meteringinfrastructure, a meter program, or any combination thereof, and whereinthe native mode and the native metering functionality platform configurethe first operational manner of the utility meter to transfer utilityinformation in compliance with the expected metering functionalityplatform.
 4. The utility metering system of claim 1, wherein saididentifying the expected metering functionality platform includesdetermining the expected metering functionality platform based on anindication sent from the metering infrastructure via the communicationnetwork.
 5. The utility metering system of claim 1, wherein the utilitymeter is configured to communicate data to the metering infrastructurevia native data tables when the utility meter operates in the nativemode, and to communicate data to the metering infrastructure viaemulated data tables when the utility meter is in the emulation mode. 6.The utility metering system of claim 1, wherein the utility meter isconfigured to emulate a display, and a user input interface of theexpected metering protocol when the utility meter is in the emulationmode.
 7. The utility metering system of claim 1, wherein the nativemetering functionality platform is stored in the utility meter as theexpected metering functionality platform during manufacture of theutility meter.
 8. The utility metering system of claim 1 wherein thesecond communication interface is configured for coupling to the meteredcomponent at the metered location and collecting metered utility datafrom the metered component related to the provided utility serviceselected from the group consisting of a sensor, a voltage collector, acurrent collector, a frequency collector, a filter, and ananalog-to-digital converter (ADC).
 9. The utility metering system ofclaim 1 wherein the utility meter receives, collects, and stores meteredutility data from the metered component independent of the stored nativemetering functionality platform.
 10. The utility metering system ofclaim 1 wherein the native metering functionality platform and theemulation metering functionality platform are further configured suchthat the second communication interface collect metered component datain compliance therewith, and the native metering functionality platformand the emulation metering functionality platform being different. 11.The utility metering system of claim 1 wherein the native meteringfunctionality platform and the emulation metering functionality platformare further configured to enable a different user interface compatibletherewith such that the displayed user data and received userinstructions are compliant with the appropriate native and emulationmetering functionality platforms.
 12. The utility metering system ofclaim 1 wherein the identifying the expected metering functionalityplatform includes transmitting a request over the first communicationinterface and receiving a response specifying the expected meteringfunctionality platform.
 13. The utility metering system of claim 1wherein the identifying the expected metering functionality platformincludes receiving a user instruction via the user interface specifyingthe expected metering functionality platform.
 14. The utility meteringsystem of claim 1 wherein the utility meter further includes a thirdinterface configured for communicating with a metered location system orprogram including one or more of collected utility data, utilityinformation, meter diagnostics, display of time of use (TOU)schedules/calendar, viewing of alerts, and usage data.
 15. The utilitymetering system of claim 1 wherein the utility meter further isconfigured for storing the emulation metering functionality platformthat is compatible with the expected metering functionality platform,and wherein the identifying the expected metering functionality platformidentifies the expected metering functionality platform to be compatiblewith the stored emulation metering functionality platform.
 16. Theutility metering system of claim 1 wherein the utility meter identifiedthe expected metering functionality platform and the comparing of theidentified the expected metering functionality indicates that the nativemetering functionality platform is different or not compatible with theexpected metering functionality platform, and wherein the utility meterdetermines that it does not have a metering functionality platform thatis stored in its memory that is compatible with the expected meteringfunctionality platform, the utility meter initiates a download over atleast one of the first and the second communication interfaces toreceive, store and operate the emulation metering functionality platformthat is compatible with the expected metering functionality platform.17. A utility meter for installation at a metered location forcollecting utility data from a metered component at said meteredlocation, the utility meter being incorporated in a utility meteringsystem coupled to metering infrastructure that monitors, collects, andtransfers utility information within the utility metering system inaccordance with an expected metering functionality platform, the utilitymeter comprising: a processor, a memory, computer executableinstructions, a first communication interface for communicativelycoupling over a communication network to the metering infrastructure, asecond communication interface for communicatively coupling to themetered component, and a user interface for displaying user data andreceiving user instructions, wherein the computer executableinstructions are configured to configure the utility meter to: receiveover the second communication interface the metered component of theutility data from the metered component; store the received meteredcomponent of the utility data in the memory; store a native meteringfunctionality platform for communicating over the first communicationinterface with the metering infrastructure; identify the expectedmetering functionality platform; compare the identified expectedmetering functionality platform with the stored native meteringfunctionality platform; operate the first communication interface andthe communicatively coupling with the metering infrastructure in anative mode when the native metering functionality platform is comparedto be the same as or compatible with the expected metering functionalityplatform, wherein the utility meter is configured to operate in a firstoperational manner in accordance with the native metering functionalityplatform, the first operational manner having first operationalfunctions including a first protocol of the first communicationinterface, a first meter operating program, a first type of the utilitydata received and stored, a first operation of the user interface of theutility meter including the first type of the utility data displayed onthe user interface; and operate in an emulation mode when the nativemetering functionality platform is not the same or is not compatiblewith the expected metering functionality platform, wherein the utilitymeter is configured to operate in a second operational manner inaccordance with an emulation metering functionality platform inconjunction with the emulation mode that is compatible with the expectedmetering functionality platform, the second operational manner includeshaving second operational functions including a second protocol of thefirst communication interface, a second meter operating program, asecond type of the utility data received and stored, a second operationof the user interface of the utility meter including a second type ofthe utility data displayed on the user interface, wherein two or more ofthe second operational functions are different than the firstoperational functions of the first operational manner of the nativemetering functionality platform.
 18. The utility meter of claim 17,wherein the processor is configured to receive a first emulationmetering functionality platform via the first communication interfaceand to store the first emulation metering functionality platform in thememory.
 19. The utility meter of claim 17, comprising meter inputs andfiltering components, wherein the meter inputs and filtering componentsare configured to collect data collected in a first non-native meteringfunctionality platform when the processor implements a first emulationmetering functionality platform.
 20. The utility meter of claim 19,comprising a display, wherein the display is configured to emulate anon-native display utilized in the first non-native meteringfunctionality platform when the processor implements the first emulationmetering functionality platform.
 21. A non-transitory tangiblecomputer-readable medium storing a plurality of instructions executableby a processor of a utility meter also including, a memory, computerexecutable instructions, wherein the computer executable instructionsare configured to configure the utility meter to: receive userinstructions, wherein the utility meter also including a firstcommunication interface for communicatively coupling to a meteringinfrastructure, a second communication interface for communicativelycoupling to a metered component at a metered location, and a userinterface for displaying user data; determine via the processor anexpected metering functionality platform of the metering infrastructurecoupled to the utility meter, wherein the metering infrastructurefacilitates information transfer with the utility meter in accordancewith the determined expected metering functionality platform; determinevia the processor whether a stored native metering functionalityplatform implemented in the utility meter is compatible with thedetermined expected metering functionality platform, the native meteringfunctionality platform relating to operation of the utility meter in afirst operational manner with the native metering functionality platformcommunicating over the first communication interface with the meteringinfrastructure, the first operational manner having first operationalfunctions including a first protocol of the first communicationinterface, a first meter operating program, a first type of the utilitydata received and stored, a first operation of the user interface of theutility meter including a first type of the utility data displayed onthe user interface; enter an emulation mode at the utility meter whenthe native metering functionality platform is not found to be not thesame or is not compatible with the expected metering functionalityplatform after comparing the expected metering functionality platformwith the stored native metering functionality platform; and implementone or more emulation metering functionality platforms at the utilitymeter to emulate functionality, interface, or both of the expectedmetering functionality platform when the utility meter is in theemulation mode, wherein the one or more emulation metering functionalityplatforms relates to the operation of the utility meter in a secondoperational manner, the second operational manner includes having secondoperational functions including a second protocol of the firstcommunication interface, a second meter operating program, a second typeof the utility data received and stored, a second operation of the userinterface of the utility meter including the second type of the utilitydata displayed on the user interface, wherein two or more of the secondoperational functions of the second operational manner are differentthan the first operational functions of the first operational manner ofthe native metering functionality platform.
 22. The medium of claim 21,wherein the computer executable instruction said to determine whetherthe native metering functionality platform implemented in the utilitymeter is compatible with the expected metering functionality platformfurther comprises first instructions to: determine whether the nativemetering functionality platform is the same as the expected meteringfunctionality platform; and determine whether the native meteringfunctionality platform is cross-compatible with the expected meteringfunctionality platform.
 23. The medium of claim 21, further comprisinginstructions to emulate a communication protocol, a user inputinterface, a display or any combination thereof utilized in the expectedmetering functionality platform when the utility meter implements theone or more emulation metering functionality platforms.
 24. The mediumof claim 21, further comprising instructions to communicate data fromthe utility meter to the metering infrastructure via an emulated datatable, wherein the emulated data table is substantially the same as adata table generated by the expected metering functionality platform.